What problem are you having?
|
Network Monitor will not start. Cause: Authenticated Users has been manually removed from the Users group. Solution: Add the Network Monitor user to the Users group following the steps described in To add a member to a local group. After the user has been added, they must log-off the computer, and then log back on. Cause: The Discretionary Access Control List (DACL) of the system directory is changed to disallow normal user's access. Solution: Add the Network Monitor user to the DACL of the system directory and assign permissions to allow normal user access by following the steps described in To assign, change, or remove permissions on Active Directory objects or attributes. |
|
Not enough disk space to create a capture buffer. Cause: When you set a capture buffer, Network Monitor reserves disk space equal to the size of the capture buffer. If not enough disk space is free, you will get an error. Solution: Make sure that the temporary capture directory has enough free disk space (at least 1 MB free + buffer size). |
|
Access denied to default capture directory on computers with lockdown policies in place. Cause: Lockdown computers will not allow you to write to files in the \Windows folder and subfolders, but the default folder for Network Monitor capture files is a subfolder of the \Windows folder. Solution: After you create a capture, save the capture into a folder to which you have read and write access. This folder becomes the new default location for saving capture files. |
|
"No NPPs found" error message. Cause: Network Monitor, the Network Monitor driver, or neither is installed properly. Solution: Make sure that the Network Monitor components are installed properly.
|